Transferring TFM/VF/PK/DVI files

reads standard TFM/VF/PK files, and reads and writes standard DVI files. If you have access to TEX on some other computer system, you should be able to move such files to and fro without any further processing. For the purposes of data transmission a TFM/VF/PK/DVI file must be treated as a binary file (a stream of arbitrary 8-bit bytes). When using Kermit to transfer binary files from another computer to your Mac, remember to type ``set file type binary'' before using the send command. The same goes for receiving such files from your Mac, but with one exception: to transfer a DVI file created by to a VAX/VMS host you'll need to type ``set file type fixed'' before using the receive command. If you have access to the Internet then there is a huge library of TFM/VF/PK files available by anonymous ftp from many archive sites. When using ftp to transfer such files, remember to type the ``binary'' command before using ``get''. If you transfer a DVI file to your Mac and a mistake occurs during transmission, or if you forgot to send it as a binary file, then will display some sort of error message soon after opening the file. Note that a DVI file contains TFM file names; this can be a cause for concern if you plan to transfer DVI files from one TEX system to another system with a different set of TFM files. Another cause of portability problems are \special commands. If you have a choice, it's always safer to transfer the original TEX input file so you can edit any incompatible font names or \special commands.